Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b50b4317dc58721c0e3d21faa4689f15cfba4de1d6e2f88291bb71614b2d07f

Tx prefix hash: 36f1b030feb17f974f353fb547aca991037ff9cdbabd3ae4beb3c8ecf2fb43f0
Tx public key: 8d5a5b8936b2d5c7ba3801eb77d433d4effe947087560eb96d151360a30356c1
Timestamp: 1709727657 Timestamp [UCT]: 2024-03-06 12:20:57 Age [y:d:h:m:s]: 01:039:09:07:24
Block: 972401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289145 RingCT/type: yes/0
Extra: 018d5a5b8936b2d5c7ba3801eb77d433d4effe947087560eb96d151360a30356c102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcbe8b4fbb0b11cd5e44a86aec1ce2f4b58b49ec828a6ea8613aeca250ca8a88 0.600000000000 1432312 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": 972411, "vin": [ { "gen": { "height": 972401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcbe8b4fbb0b11cd5e44a86aec1ce2f4b58b49ec828a6ea8613aeca250ca8a88" } } ], "extra": [ 1, 141, 90, 91, 137, 54, 178, 213, 199, 186, 56, 1, 235, 119, 212, 51, 212, 239, 254, 148, 112, 135, 86, 14, 185, 109, 21, 19, 96, 163, 3, 86, 193, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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