Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ecdc97f5324763dee21f2cbd3eb6f53c07eb8cb42464a9b3f8c1a4ab12eebf

Tx prefix hash: c7ae87676a719ea16f1cb275fa9f5c8c624a6055268870e5e4eb78f525a598fc
Tx public key: 7fbef82aa1b806c5d47af5493e28406e7c44217a4ccf841ab93caa2e4b275416
Timestamp: 1737728337 Timestamp [UCT]: 2025-01-24 14:18:57 Age [y:d:h:m:s]: 00:332:08:14:49
Block: 1204339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235105 RingCT/type: yes/0
Extra: 017fbef82aa1b806c5d47af5493e28406e7c44217a4ccf841ab93caa2e4b2754160211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 320dd5687bdcb428d3eaa189ac18eeb77309eecb3dc0620ea4595dc1b91a6abf 0.600000000000 1691024 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": 1204349, "vin": [ { "gen": { "height": 1204339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "320dd5687bdcb428d3eaa189ac18eeb77309eecb3dc0620ea4595dc1b91a6abf" } } ], "extra": [ 1, 127, 190, 248, 42, 161, 184, 6, 197, 212, 122, 245, 73, 62, 40, 64, 110, 124, 68, 33, 122, 76, 207, 132, 26, 185, 60, 170, 46, 75, 39, 84, 22, 2, 17, 0, 0, 0, 1, 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