Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da07f420f0ac409f6aa78646102c6d6f925f6f89ede3cf365d8a4a651503b721

Tx prefix hash: 77dbe069e3da8579636b6d874ac7429cedc4e8002899a58bccad028af3c7bfbb
Tx public key: 4adf85cd066d5494e51cd6493a1ceddc79ac18bb1a28a968fe524d46c8b1b5b7
Timestamp: 1729099412 Timestamp [UCT]: 2024-10-16 17:23:32 Age [y:d:h:m:s]: 00:038:15:59:03
Block: 1132989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27599 RingCT/type: yes/0
Extra: 014adf85cd066d5494e51cd6493a1ceddc79ac18bb1a28a968fe524d46c8b1b5b70211000000043cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d7fc2319187c9d49b8e0ebcdbc4ceb160682d3226c3bfc316630b1623bf767a 0.600000000000 1616048 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": 1132999, "vin": [ { "gen": { "height": 1132989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d7fc2319187c9d49b8e0ebcdbc4ceb160682d3226c3bfc316630b1623bf767a" } } ], "extra": [ 1, 74, 223, 133, 205, 6, 109, 84, 148, 229, 28, 214, 73, 58, 28, 237, 220, 121, 172, 24, 187, 26, 40, 169, 104, 254, 82, 77, 70, 200, 177, 181, 183, 2, 17, 0, 0, 0, 4, 60, 208, 252, 6, 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