Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 836e63752193c5ecd1d47e25677bd01d2c0eaac2de03398bc78c37eb60331dc0

Tx prefix hash: 98b1997012fff6547e67205313a058ded87799d75eef4f539cd584f859d1a1ae
Tx public key: 1a3b184e318cdd746e798f51966572671d98f95fb5d32234438f17861fde0371
Timestamp: 1625627611 Timestamp [UCT]: 2021-07-07 03:13:31 Age [y:d:h:m:s]: 03:141:16:43:49
Block: 289441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871471 RingCT/type: yes/0
Extra: 011a3b184e318cdd746e798f51966572671d98f95fb5d32234438f17861fde0371021100000029d2c85fae000000000000000000

1 output(s) for total of 67.451940768000 dcy

stealth address amount amount idx
00: 88946b163f46423194a052e5f319e43580b53e2d28545b774131f7e38ad4bc39 67.451940768000 606199 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": 289451, "vin": [ { "gen": { "height": 289441 } } ], "vout": [ { "amount": 67451940768, "target": { "key": "88946b163f46423194a052e5f319e43580b53e2d28545b774131f7e38ad4bc39" } } ], "extra": [ 1, 26, 59, 24, 78, 49, 140, 221, 116, 110, 121, 143, 81, 150, 101, 114, 103, 29, 152, 249, 95, 181, 211, 34, 52, 67, 143, 23, 134, 31, 222, 3, 113, 2, 17, 0, 0, 0, 41, 210, 200, 95, 174, 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