Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4ba28a9877a9fc3f9287bb03847d441555c59995973e9df4375b2f60c8de35

Tx prefix hash: 020fc8f3a741e3c53c06582cb90f15c6be08999326a59fe289f7ede254ac37b3
Tx public key: ebc23945f736d08b7bd7a53f0794c45bf2397ec706a9110e8f6aac8b97228527
Timestamp: 1763349958 Timestamp [UCT]: 2025-11-17 03:25:58 Age [y:d:h:m:s]: 00:076:07:36:02
Block: 1413817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54465 RingCT/type: yes/0
Extra: 01ebc23945f736d08b7bd7a53f0794c45bf2397ec706a9110e8f6aac8b97228527021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 003ecd7bddb2bf956f189c24efc7e5cd6e9c076636faf46980b78d092736436e 0.600000000000 1902298 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": 1413827, "vin": [ { "gen": { "height": 1413817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "003ecd7bddb2bf956f189c24efc7e5cd6e9c076636faf46980b78d092736436e" } } ], "extra": [ 1, 235, 194, 57, 69, 247, 54, 208, 139, 123, 215, 165, 63, 7, 148, 196, 91, 242, 57, 126, 199, 6, 169, 17, 14, 143, 106, 172, 139, 151, 34, 133, 39, 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