Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd55cb1e64fcfcdc11e87c99e3d0e899f0b66379ca7cce978462777ef531d7c

Tx prefix hash: ea97963867068a64244d8d5c59295c6b06569aa08ef47d2ecf9db20bc6b1e163
Tx public key: 98a0b7e7ebdea2d045c420b2e8fca9151772b462861c53ff8533420418dc5645
Timestamp: 1702692211 Timestamp [UCT]: 2023-12-16 02:03:31 Age [y:d:h:m:s]: 01:129:22:01:52
Block: 914063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353987 RingCT/type: yes/0
Extra: 0198a0b7e7ebdea2d045c420b2e8fca9151772b462861c53ff8533420418dc5645021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e438ef7095016eb19f57c35f32dcf33e05a98b75304a01ea1fd80a819fd8e70 0.600000000000 1371345 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": 914073, "vin": [ { "gen": { "height": 914063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e438ef7095016eb19f57c35f32dcf33e05a98b75304a01ea1fd80a819fd8e70" } } ], "extra": [ 1, 152, 160, 183, 231, 235, 222, 162, 208, 69, 196, 32, 178, 232, 252, 169, 21, 23, 114, 180, 98, 134, 28, 83, 255, 133, 51, 66, 4, 24, 220, 86, 69, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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