Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde07ce97ffa7c0e681185822f9aa5b6c06457b7d8053b33265b562691ac55fa

Tx prefix hash: 35f83d1e59da90bc77032165984ed5de5f60e0dfabd8cb40d4b7320eb69803c4
Tx public key: 97923fda6c65149e85070d9e0a7565432d70b99f94a37b904bf9f9d8308a99c3
Timestamp: 1764203088 Timestamp [UCT]: 2025-11-27 00:24:48 Age [y:d:h:m:s]: 00:007:02:23:13
Block: 1420891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5081 RingCT/type: yes/0
Extra: 0197923fda6c65149e85070d9e0a7565432d70b99f94a37b904bf9f9d8308a99c3021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06f8ebb9a216590b5638c09e2899c2aac42df770b461f4e40e903a61299df0ec 0.600000000000 1909446 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": 1420901, "vin": [ { "gen": { "height": 1420891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06f8ebb9a216590b5638c09e2899c2aac42df770b461f4e40e903a61299df0ec" } } ], "extra": [ 1, 151, 146, 63, 218, 108, 101, 20, 158, 133, 7, 13, 158, 10, 117, 101, 67, 45, 112, 185, 159, 148, 163, 123, 144, 75, 249, 249, 216, 48, 138, 153, 195, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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