Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f1487ee9000a53a7774055a6bbdc4846a2e2242d61d916ec60a891f1d757cb1

Tx prefix hash: da4050262806e123d09e280e8711fc87b72983c81074958856dcb2d06f67efc0
Tx public key: 5b1b7f2a064ae64f7f281fea35801d7d30906ce60435529c876fe38e258c8a4a
Timestamp: 1712659874 Timestamp [UCT]: 2024-04-09 10:51:14 Age [y:d:h:m:s]: 00:288:15:34:25
Block: 996684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206579 RingCT/type: yes/0
Extra: 015b1b7f2a064ae64f7f281fea35801d7d30906ce60435529c876fe38e258c8a4a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 994495857090ef56c37e9407b92291700a9b855ae50de6cc2abb18f28669ae70 0.600000000000 1457110 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": 996694, "vin": [ { "gen": { "height": 996684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "994495857090ef56c37e9407b92291700a9b855ae50de6cc2abb18f28669ae70" } } ], "extra": [ 1, 91, 27, 127, 42, 6, 74, 230, 79, 127, 40, 31, 234, 53, 128, 29, 125, 48, 144, 108, 230, 4, 53, 82, 156, 135, 111, 227, 142, 37, 140, 138, 74, 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