Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6b92818651133d2d8045ddce26066539780f1f42eb7b02f789ecc3d910922d7c

Tx prefix hash: 99fc0b26889e6a6636108d662538aaf482c4e7db5da959e706e0617bd154332e
Tx public key: b0fa6bcecc4ed11b8b3346801eec31995900be398b3cf0947d5c9a97e86e1753
Timestamp: 1576469429 Timestamp [UCT]: 2019-12-16 04:10:29 Age [y:d:h:m:s]: 05:321:03:50:07
Block: 27892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1373906 RingCT/type: yes/0
Extra: 01b0fa6bcecc4ed11b8b3346801eec31995900be398b3cf0947d5c9a97e86e17530211000000088a2ee0d9000000000000000000

1 output(s) for total of 496.124387064000 dcy

stealth address amount amount idx
00: 1726c9d991cf79839fbdb55964d2e8f82e2bff4d1cf772ad1c417df756f9255b 496.124387064000 46074 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 27902, "vin": [ { "gen": { "height": 27892 } } ], "vout": [ { "amount": 496124387064, "target": { "key": "1726c9d991cf79839fbdb55964d2e8f82e2bff4d1cf772ad1c417df756f9255b" } } ], "extra": [ 1, 176, 250, 107, 206, 204, 78, 209, 27, 139, 51, 70, 128, 30, 236, 49, 153, 89, 0, 190, 57, 139, 60, 240, 148, 125, 92, 154, 151, 232, 110, 23, 83, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8