Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f15c3d8ee944e4d73486aebcfc77279e274926430eec0ca00e8595b8858b96

Tx prefix hash: c880766e4ea86afa6cb0491ba1326e061e33e1a1b067b1c76de33b577988cd1e
Tx public key: 009119317c9e3b224e846776db469e43e1ed9dc973527a76ce03e8450cc59df4
Timestamp: 1707920277 Timestamp [UCT]: 2024-02-14 14:17:57 Age [y:d:h:m:s]: 01:055:15:17:57
Block: 957396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300816 RingCT/type: yes/0
Extra: 01009119317c9e3b224e846776db469e43e1ed9dc973527a76ce03e8450cc59df402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b8d3dcffdbb6335e7cce61a3e38738b48b5fad0dc091d667277659b7b0bbf3a 0.600000000000 1416714 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": 957406, "vin": [ { "gen": { "height": 957396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b8d3dcffdbb6335e7cce61a3e38738b48b5fad0dc091d667277659b7b0bbf3a" } } ], "extra": [ 1, 0, 145, 25, 49, 124, 158, 59, 34, 78, 132, 103, 118, 219, 70, 158, 67, 225, 237, 157, 201, 115, 82, 122, 118, 206, 3, 232, 69, 12, 197, 157, 244, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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