Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13908229c8ae7817d04c57e7333aee65f7fcc9ce06c36cfc8c6daed5e008a0c6

Tx prefix hash: f974466daed9beacfc55dcefe6a720c8fd648df5ae30050da21cef584b01fb00
Tx public key: 0eb0b5f90d38a78d9bafd03ab3067d0d5718efa1dcbc458fcf5f0058f06bf215
Timestamp: 1766164504 Timestamp [UCT]: 2025-12-19 17:15:04 Age [y:d:h:m:s]: 00:002:14:32:48
Block: 1437151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1850 RingCT/type: yes/0
Extra: 010eb0b5f90d38a78d9bafd03ab3067d0d5718efa1dcbc458fcf5f0058f06bf2150211000000067b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77a65fca037ce8e78830063d1dc58cc62039aff264e69159dd01f8974cd01fc1 0.600000000000 1925956 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": 1437161, "vin": [ { "gen": { "height": 1437151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77a65fca037ce8e78830063d1dc58cc62039aff264e69159dd01f8974cd01fc1" } } ], "extra": [ 1, 14, 176, 181, 249, 13, 56, 167, 141, 155, 175, 208, 58, 179, 6, 125, 13, 87, 24, 239, 161, 220, 188, 69, 143, 207, 95, 0, 88, 240, 107, 242, 21, 2, 17, 0, 0, 0, 6, 123, 30, 81, 172, 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