Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f626144736480edfde15ab0b0290a1a14b8c7c66752bbdfba05282aec3f8827

Tx prefix hash: e64b00f46c97c00e3cc2f30144be9f46710ce499ba1370b4612bec864650efd3
Tx public key: d7305d97837c5b99d4e0b2a38ac0cf9a778fc822d68aea8fc8be3fd3064d7663
Timestamp: 1763124182 Timestamp [UCT]: 2025-11-14 12:43:02 Age [y:d:h:m:s]: 00:007:01:26:39
Block: 1411953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5042 RingCT/type: yes/0
Extra: 01d7305d97837c5b99d4e0b2a38ac0cf9a778fc822d68aea8fc8be3fd3064d76630211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c31c7431f3927cb88ea56c7e74456d71b5a31ec3f81a4dc555f8947db0fabec 0.600000000000 1900418 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": 1411963, "vin": [ { "gen": { "height": 1411953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c31c7431f3927cb88ea56c7e74456d71b5a31ec3f81a4dc555f8947db0fabec" } } ], "extra": [ 1, 215, 48, 93, 151, 131, 124, 91, 153, 212, 224, 178, 163, 138, 192, 207, 154, 119, 143, 200, 34, 214, 138, 234, 143, 200, 190, 63, 211, 6, 77, 118, 99, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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