Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd963a38066c2eea9f984de6b4c45b0eba3ba46473fac753e8a310bb067d57b9

Tx prefix hash: 96c0f006fc9983ddfc1a164041540209e1659e5f25b53306f8c1d80243216ebe
Tx public key: 93c68cdf93f426146a8012f329fdd1f48306d1cbb8c37f4a4d88efc1d32395cb
Timestamp: 1721973816 Timestamp [UCT]: 2024-07-26 06:03:36 Age [y:d:h:m:s]: 00:308:19:25:48
Block: 1073912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220664 RingCT/type: yes/0
Extra: 0193c68cdf93f426146a8012f329fdd1f48306d1cbb8c37f4a4d88efc1d32395cb02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f98c6a56fe7ca17e69e433eafdbf5a7c763832fd59f94088d3f603071745981b 0.600000000000 1546421 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": 1073922, "vin": [ { "gen": { "height": 1073912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f98c6a56fe7ca17e69e433eafdbf5a7c763832fd59f94088d3f603071745981b" } } ], "extra": [ 1, 147, 198, 140, 223, 147, 244, 38, 20, 106, 128, 18, 243, 41, 253, 209, 244, 131, 6, 209, 203, 184, 195, 127, 74, 77, 136, 239, 193, 211, 35, 149, 203, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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