Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4ef6b971d5b9f3527e695983da82e6edc9cbbf103f488bc34040e73bd89dd4

Tx prefix hash: 1fd706cb03525875669d52d1b2c33b72ba28c7a5b9c096ff1aa6864174e10e6d
Tx public key: 5bdfd8b50016dbd4eff5367b616aee7704cbed4bc100ceec18429e3e9a7d793a
Timestamp: 1701251489 Timestamp [UCT]: 2023-11-29 09:51:29 Age [y:d:h:m:s]: 00:362:08:57:27
Block: 902117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259473 RingCT/type: yes/0
Extra: 015bdfd8b50016dbd4eff5367b616aee7704cbed4bc100ceec18429e3e9a7d793a02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.629378456000 dcy

stealth address amount amount idx
00: 09530f0831b1da21cf3fded6a0a228dd4eaabef8c191c09667c9cf3d19e7ecfb 0.629378456000 1358730 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": 902127, "vin": [ { "gen": { "height": 902117 } } ], "vout": [ { "amount": 629378456, "target": { "key": "09530f0831b1da21cf3fded6a0a228dd4eaabef8c191c09667c9cf3d19e7ecfb" } } ], "extra": [ 1, 91, 223, 216, 181, 0, 22, 219, 212, 239, 245, 54, 123, 97, 106, 238, 119, 4, 203, 237, 75, 193, 0, 206, 236, 24, 66, 158, 62, 154, 125, 121, 58, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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