Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e6f25f348d2be13e04887fdb4158f8a87d12f5202939a940f693e9c5718969

Tx prefix hash: 403cc2360bef4125de91cadc814b0627bf2f4d51aaebc4e928e106ddfc519ef1
Tx public key: 577ab2db622ce9106ead2f06fd3d4fdbe0149ab7af0b96aa92168781d862b381
Timestamp: 1723641444 Timestamp [UCT]: 2024-08-14 13:17:24 Age [y:d:h:m:s]: 00:237:06:43:15
Block: 1087751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169455 RingCT/type: yes/0
Extra: 01577ab2db622ce9106ead2f06fd3d4fdbe0149ab7af0b96aa92168781d862b38102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50743ba09e6af0b46586422163f5dfe93d64a63ff9172e3f04ec4f1dc7cb7def 0.600000000000 1562362 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": 1087761, "vin": [ { "gen": { "height": 1087751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50743ba09e6af0b46586422163f5dfe93d64a63ff9172e3f04ec4f1dc7cb7def" } } ], "extra": [ 1, 87, 122, 178, 219, 98, 44, 233, 16, 110, 173, 47, 6, 253, 61, 79, 219, 224, 20, 154, 183, 175, 11, 150, 170, 146, 22, 135, 129, 216, 98, 179, 129, 2, 17, 0, 0, 0, 8, 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