Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6730d0a7be027c5e608b2062d590d1e1f0960e8bf847860e1580473eb1604667

Tx prefix hash: 65b4eae30f3ca5302d0d4de182a1c69d2b8cf6d0cf7f83f72719e892ffa482c0
Tx public key: 32bb531f67e07b14490092a804b837e966abdbd0be55355e7c2c2f5b01d105a8
Timestamp: 1737155300 Timestamp [UCT]: 2025-01-17 23:08:20 Age [y:d:h:m:s]: 00:152:01:29:23
Block: 1199627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108381 RingCT/type: yes/0
Extra: 0132bb531f67e07b14490092a804b837e966abdbd0be55355e7c2c2f5b01d105a80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a99c4400d4437448c92fe45e8147a78f9677af6a0e547538fd583e92c225826b 0.600000000000 1686260 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": 1199637, "vin": [ { "gen": { "height": 1199627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a99c4400d4437448c92fe45e8147a78f9677af6a0e547538fd583e92c225826b" } } ], "extra": [ 1, 50, 187, 83, 31, 103, 224, 123, 20, 73, 0, 146, 168, 4, 184, 55, 233, 102, 171, 219, 208, 190, 85, 53, 94, 124, 44, 47, 91, 1, 209, 5, 168, 2, 17, 0, 0, 0, 3, 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