Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9f29606533cc1ec6cc90208ddc2b3c63703c5c03f034fad978d97c9383fcc19

Tx prefix hash: fb0f6f3f2a42570507a65a3e86ea8954be6953cd0715099ddc299ac18d7bf245
Tx public key: 0ba785ef63576fb4473d72f17b5c86a3b299b0b34be2caf4a9c9510a265d7938
Timestamp: 1737502253 Timestamp [UCT]: 2025-01-21 23:30:53 Age [y:d:h:m:s]: 00:148:00:57:04
Block: 1202464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105544 RingCT/type: yes/0
Extra: 010ba785ef63576fb4473d72f17b5c86a3b299b0b34be2caf4a9c9510a265d7938021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83239cc018a80a6ff9a75dab04b514157d3b69bdac13f84d31ccd98bf386fc70 0.600000000000 1689129 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": 1202474, "vin": [ { "gen": { "height": 1202464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83239cc018a80a6ff9a75dab04b514157d3b69bdac13f84d31ccd98bf386fc70" } } ], "extra": [ 1, 11, 167, 133, 239, 99, 87, 111, 180, 71, 61, 114, 241, 123, 92, 134, 163, 178, 153, 176, 179, 75, 226, 202, 244, 169, 201, 81, 10, 38, 93, 121, 56, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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