Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc456bdc50aacf03da8cc9dfa930cb7ba19af8a81745e72ced0a654b8cd072d

Tx prefix hash: 652c100413156eca1f959e0dbbc504a9cf6c57146fcdaa495576490d34c425f6
Tx public key: 45a45cd7f1de156c55f96d87aaf3533a1233b5d6bbfa46c7a591d2b994b50c23
Timestamp: 1760872162 Timestamp [UCT]: 2025-10-19 11:09:22 Age [y:d:h:m:s]: 00:068:06:34:18
Block: 1393305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48861 RingCT/type: yes/0
Extra: 0145a45cd7f1de156c55f96d87aaf3533a1233b5d6bbfa46c7a591d2b994b50c23021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f20ec4891b0f58f063801d220bdb146799b0ceaadbaa00862b4ab9a7d9dead99 0.600000000000 1881568 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": 1393315, "vin": [ { "gen": { "height": 1393305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f20ec4891b0f58f063801d220bdb146799b0ceaadbaa00862b4ab9a7d9dead99" } } ], "extra": [ 1, 69, 164, 92, 215, 241, 222, 21, 108, 85, 249, 109, 135, 170, 243, 83, 58, 18, 51, 181, 214, 187, 250, 70, 199, 165, 145, 210, 185, 148, 181, 12, 35, 2, 17, 0, 0, 0, 1, 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