Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eb0e750b29f524d8c7e12b4f6847cfde29d10a1bc280f761ae42c00e157fed1

Tx prefix hash: dced0c3ff7e7b2c751f12ff289bb9a81094b0850d533dba08c4b76f286f4d82b
Tx public key: 8035e683f88113eb396d8f68d69ab1192fc554b85eab83b74e1279d5a9536836
Timestamp: 1621621785 Timestamp [UCT]: 2021-05-21 18:29:45 Age [y:d:h:m:s]: 03:193:02:44:02
Block: 264652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899874 RingCT/type: yes/0
Extra: 018035e683f88113eb396d8f68d69ab1192fc554b85eab83b74e1279d5a95368360211000000196e2c823c000000000000000000

1 output(s) for total of 81.488927753000 dcy

stealth address amount amount idx
00: a74b093b270262700b952396f68684ee7f8f5a1d156d245197998638ce331e60 81.488927753000 556450 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": 264662, "vin": [ { "gen": { "height": 264652 } } ], "vout": [ { "amount": 81488927753, "target": { "key": "a74b093b270262700b952396f68684ee7f8f5a1d156d245197998638ce331e60" } } ], "extra": [ 1, 128, 53, 230, 131, 248, 129, 19, 235, 57, 109, 143, 104, 214, 154, 177, 25, 47, 197, 84, 184, 94, 171, 131, 183, 78, 18, 121, 213, 169, 83, 104, 54, 2, 17, 0, 0, 0, 25, 110, 44, 130, 60, 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