Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 014d61e5009ba647e06e59a83146aff0486f72c0bf35a6b62ca76dbb448df964

Tx prefix hash: 227c0fc1866ca5eba3952133a0d6859503270ca1d64c652a674a1c9ebc7c996b
Tx public key: 73aa4e2f50331a5c897c3f6fc780b102e6f398854c08c95f945013ae06354f24
Timestamp: 1758315349 Timestamp [UCT]: 2025-09-19 20:55:49 Age [y:d:h:m:s]: 00:062:18:59:49
Block: 1372095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44948 RingCT/type: yes/0
Extra: 0173aa4e2f50331a5c897c3f6fc780b102e6f398854c08c95f945013ae06354f24021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0b9dcc26edd565d3b641c5966979613a33044b39ab812a107b93c0fdf8a85a 0.600000000000 1860180 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": 1372105, "vin": [ { "gen": { "height": 1372095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0b9dcc26edd565d3b641c5966979613a33044b39ab812a107b93c0fdf8a85a" } } ], "extra": [ 1, 115, 170, 78, 47, 80, 51, 26, 92, 137, 124, 63, 111, 199, 128, 177, 2, 230, 243, 152, 133, 76, 8, 201, 95, 148, 80, 19, 174, 6, 53, 79, 36, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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