Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eccf7ae7a9f5c6006cd0ddbb509c2fd8e71cf60fce735a2b239cfbc0689bd394

Tx prefix hash: 5f34e5cb8b2899315de19b7ba3ddc5c255ac92748460106b6c27e6ec10ad0a75
Tx public key: 16d7a638633338d18dc63c441072fc54c891e8a18fc4427209a821d6b622e2d8
Timestamp: 1763161293 Timestamp [UCT]: 2025-11-14 23:01:33 Age [y:d:h:m:s]: 00:013:10:57:57
Block: 1412260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9634 RingCT/type: yes/0
Extra: 0116d7a638633338d18dc63c441072fc54c891e8a18fc4427209a821d6b622e2d80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f2778c3b5604d0b9a47d74bdfb8b3421074f3322f2a01750de2216610fdb1a5 0.600000000000 1900727 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": 1412270, "vin": [ { "gen": { "height": 1412260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f2778c3b5604d0b9a47d74bdfb8b3421074f3322f2a01750de2216610fdb1a5" } } ], "extra": [ 1, 22, 215, 166, 56, 99, 51, 56, 209, 141, 198, 60, 68, 16, 114, 252, 84, 200, 145, 232, 161, 143, 196, 66, 114, 9, 168, 33, 214, 182, 34, 226, 216, 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