Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d687a97d0f85b94139cea10f6a39fdb74426d2b77b5b78fa3271e455b1941d2

Tx prefix hash: d1671cc42a37afbfc6dcd95a7c404b1c07806bb07877199afeb14cc16b34f898
Tx public key: 8004030412e612bcf0a66ec6e9379f0a2631478db1652f428869c1e54d3780a4
Timestamp: 1758740668 Timestamp [UCT]: 2025-09-24 19:04:28 Age [y:d:h:m:s]: 00:058:00:00:30
Block: 1375624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41523 RingCT/type: yes/0
Extra: 018004030412e612bcf0a66ec6e9379f0a2631478db1652f428869c1e54d3780a402110000000db2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82f5be7dd2e3b94cb4b936f9fb003e5399d1ec5b704f8d9bc9f3c7ec893d5e42 0.600000000000 1863715 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": 1375634, "vin": [ { "gen": { "height": 1375624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82f5be7dd2e3b94cb4b936f9fb003e5399d1ec5b704f8d9bc9f3c7ec893d5e42" } } ], "extra": [ 1, 128, 4, 3, 4, 18, 230, 18, 188, 240, 166, 110, 198, 233, 55, 159, 10, 38, 49, 71, 141, 177, 101, 47, 66, 136, 105, 193, 229, 77, 55, 128, 164, 2, 17, 0, 0, 0, 13, 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