Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb3d9ec444fd080e91dd25477a637f978e95ea591033df59a6adf0ad54e0dafc

Tx prefix hash: bd62c10f0b78626d55021052130a50babc4d0351916c437441ee7b5a1b1bb72c
Tx public key: b78288a47da0eaacf3d7a6101a318595e3bd21fcff2e2b52374ed40a66f1bd24
Timestamp: 1714385065 Timestamp [UCT]: 2024-04-29 10:04:25 Age [y:d:h:m:s]: 00:305:00:29:28
Block: 1011003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218012 RingCT/type: yes/0
Extra: 01b78288a47da0eaacf3d7a6101a318595e3bd21fcff2e2b52374ed40a66f1bd2402110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53f13e66341715cd2bff91d176ffd84f19667a4d94f08225d8cdc58544a8837d 0.600000000000 1473113 of 15

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": 1011013, "vin": [ { "gen": { "height": 1011003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53f13e66341715cd2bff91d176ffd84f19667a4d94f08225d8cdc58544a8837d" } } ], "extra": [ 1, 183, 130, 136, 164, 125, 160, 234, 172, 243, 215, 166, 16, 26, 49, 133, 149, 227, 189, 33, 252, 255, 46, 43, 82, 55, 78, 212, 10, 102, 241, 189, 36, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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