Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce9760d9c6aead220f114a7dfb66490de6ae3a7ece5d65363554a8da5365dee7

Tx prefix hash: 44a3340d93440a1821b06b3d5d224b517031996d5ed2c808a0425201eceaad7c
Tx public key: 9588f5433965aedae027fd72555a7ea7eea7e188c1f69de4e5dccfcf7c78b4c8
Timestamp: 1736179770 Timestamp [UCT]: 2025-01-06 16:09:30 Age [y:d:h:m:s]: 00:092:00:34:28
Block: 1191570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65537 RingCT/type: yes/0
Extra: 019588f5433965aedae027fd72555a7ea7eea7e188c1f69de4e5dccfcf7c78b4c8021100000012007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fda94444999a707d8dd5cbb61f159d7f643d760b224abdab41188a2539967d4 0.600000000000 1678109 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": 1191580, "vin": [ { "gen": { "height": 1191570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fda94444999a707d8dd5cbb61f159d7f643d760b224abdab41188a2539967d4" } } ], "extra": [ 1, 149, 136, 245, 67, 57, 101, 174, 218, 224, 39, 253, 114, 85, 90, 126, 167, 238, 167, 225, 136, 193, 246, 157, 228, 229, 220, 207, 207, 124, 120, 180, 200, 2, 17, 0, 0, 0, 18, 0, 127, 151, 138, 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