Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24343613c64865dc92e068eb168e13a34af1b0ae312adeb75f09fdec0bd0036

Tx prefix hash: b0d89bbfc7bcfe19aff5c90fde2650699d5b6a9b473b6234a79c91ce3da685d4
Tx public key: e9bd9fd51c8a2c364f3dec2a214d6440e5dfa47db33500b8f73fa0671217039c
Timestamp: 1718315275 Timestamp [UCT]: 2024-06-13 21:47:55 Age [y:d:h:m:s]: 01:147:07:31:51
Block: 1043591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363848 RingCT/type: yes/0
Extra: 01e9bd9fd51c8a2c364f3dec2a214d6440e5dfa47db33500b8f73fa0671217039c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e803bc80dc5d28036366f4eb38edc245fc0c866c4d6a3927035db34c09149a 0.600000000000 1512748 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": 1043601, "vin": [ { "gen": { "height": 1043591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e803bc80dc5d28036366f4eb38edc245fc0c866c4d6a3927035db34c09149a" } } ], "extra": [ 1, 233, 189, 159, 213, 28, 138, 44, 54, 79, 61, 236, 42, 33, 77, 100, 64, 229, 223, 164, 125, 179, 53, 0, 184, 247, 63, 160, 103, 18, 23, 3, 156, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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