Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 670b44c62af50b67e1227c4f85cb699934ba478efc726852df00ccd8af4b9c0f

Tx prefix hash: c164710127d237c849595a5c58f78500fa4baa281712a2f4446159618be80a44
Tx public key: 2110d6854d1e4ce8477746fcb8eb4ca1e6be8897dd8f06595ac1cff2e2657ad2
Timestamp: 1749939431 Timestamp [UCT]: 2025-06-14 22:17:11 Age [y:d:h:m:s]: 00:164:18:06:34
Block: 1305122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115538 RingCT/type: yes/0
Extra: 012110d6854d1e4ce8477746fcb8eb4ca1e6be8897dd8f06595ac1cff2e2657ad2021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5e628b0e39dee823c7d5573dff1675afe4b4bf822a3e80f3720c6d75b21f160 0.600000000000 1792721 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": 1305132, "vin": [ { "gen": { "height": 1305122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5e628b0e39dee823c7d5573dff1675afe4b4bf822a3e80f3720c6d75b21f160" } } ], "extra": [ 1, 33, 16, 214, 133, 77, 30, 76, 232, 71, 119, 70, 252, 184, 235, 76, 161, 230, 190, 136, 151, 221, 143, 6, 89, 90, 193, 207, 242, 226, 101, 122, 210, 2, 17, 0, 0, 0, 2, 228, 220, 144, 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