Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96f4c6e95c9e0c4e32ae46819ae930e5d03603dd542a4a70fe55725cdbfafb23

Tx prefix hash: 463a03a0615ecc5766d942941e773aaa1e41f8b4304d3b8422bb2ca43b8457ce
Tx public key: 66eefc4c57e9cf42f86ae012235dd3143aec99537ff60ae60ea86b5040dce80a
Timestamp: 1734022852 Timestamp [UCT]: 2024-12-12 17:00:52 Age [y:d:h:m:s]: 00:109:16:28:20
Block: 1173727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78154 RingCT/type: yes/0
Extra: 0166eefc4c57e9cf42f86ae012235dd3143aec99537ff60ae60ea86b5040dce80a0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a13d777a9af8cc1ae791c5f4a4f35d7bffb66a791dace58ebac0bc57dbe670db 0.600000000000 1659780 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": 1173737, "vin": [ { "gen": { "height": 1173727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a13d777a9af8cc1ae791c5f4a4f35d7bffb66a791dace58ebac0bc57dbe670db" } } ], "extra": [ 1, 102, 238, 252, 76, 87, 233, 207, 66, 248, 106, 224, 18, 35, 93, 211, 20, 58, 236, 153, 83, 127, 246, 10, 230, 14, 168, 107, 80, 64, 220, 232, 10, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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