Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64fc0be16774bb871839dbd4141acdc8e6a767972fc5e7285e5c5d22effe81d0

Tx prefix hash: a47d592e9a602e7af8c4cb54db3d6aca6714c98a5da7999c3dbc7565f358ead6
Tx public key: c992a7e8572f7351bef606a1b6a2356bc229edeb58378eb804f982bd73d5f3f0
Timestamp: 1755236328 Timestamp [UCT]: 2025-08-15 05:38:48 Age [y:d:h:m:s]: 00:098:18:42:47
Block: 1347023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70281 RingCT/type: yes/0
Extra: 01c992a7e8572f7351bef606a1b6a2356bc229edeb58378eb804f982bd73d5f3f0021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86e72aee51d0d0447e1589a1153f084572b124fd3959cb9014f2e9aa56ed22bd 0.600000000000 1834936 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": 1347033, "vin": [ { "gen": { "height": 1347023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86e72aee51d0d0447e1589a1153f084572b124fd3959cb9014f2e9aa56ed22bd" } } ], "extra": [ 1, 201, 146, 167, 232, 87, 47, 115, 81, 190, 246, 6, 161, 182, 162, 53, 107, 194, 41, 237, 235, 88, 55, 142, 184, 4, 249, 130, 189, 115, 213, 243, 240, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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