Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a14a2ccb95e1d83fd7c4aaf7207d1ad91fcf8d9103e93c2146fd7b47b026509

Tx prefix hash: c05edb4dcd28141f03d247689190ee766855d410d3393e2da361599110cd785a
Tx public key: 2f7fbf824776fc4de52a6bfadb5ae02fb97e539e69afe0a1d17d85c989ddc323
Timestamp: 1763393407 Timestamp [UCT]: 2025-11-17 15:30:07 Age [y:d:h:m:s]: 00:036:01:12:21
Block: 1414181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25796 RingCT/type: yes/0
Extra: 012f7fbf824776fc4de52a6bfadb5ae02fb97e539e69afe0a1d17d85c989ddc3230211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a37c545c741f53e694a2c8715532292eab10d0a2519e72c2ce11022886e2888 0.600000000000 1902668 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": 1414191, "vin": [ { "gen": { "height": 1414181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a37c545c741f53e694a2c8715532292eab10d0a2519e72c2ce11022886e2888" } } ], "extra": [ 1, 47, 127, 191, 130, 71, 118, 252, 77, 229, 42, 107, 250, 219, 90, 224, 47, 185, 126, 83, 158, 105, 175, 224, 161, 209, 125, 133, 201, 137, 221, 195, 35, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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