Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03624cd5c23400434e5e9945ffb7c5692fa42b1926617fb5edfa9dfb5e4ec5da

Tx prefix hash: 9b57ce79c7667513482ed629bf0ea6d44ea5ddfe0cf2f9122e95662643c78ea6
Tx public key: d981fccf41d5128c4d98e14aa6615664033a15b3c874da7bcf89a7cd4ed82f5d
Timestamp: 1704186742 Timestamp [UCT]: 2024-01-02 09:12:22 Age [y:d:h:m:s]: 01:017:02:54:18
Block: 926447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273569 RingCT/type: yes/0
Extra: 01d981fccf41d5128c4d98e14aa6615664033a15b3c874da7bcf89a7cd4ed82f5d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c23aa2784a012a47872ed29f23c1c08cc05f064fd96e3596437402d6afc2c19e 0.600000000000 1384231 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": 926457, "vin": [ { "gen": { "height": 926447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c23aa2784a012a47872ed29f23c1c08cc05f064fd96e3596437402d6afc2c19e" } } ], "extra": [ 1, 217, 129, 252, 207, 65, 213, 18, 140, 77, 152, 225, 74, 166, 97, 86, 100, 3, 58, 21, 179, 200, 116, 218, 123, 207, 137, 167, 205, 78, 216, 47, 93, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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