Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b7d7be118ff833bffd50872c834c46d6a2dd25ba753f3a3489cc4fc8bdf65e8

Tx prefix hash: 0c9cfab74678165a75245384b0e26a3e491e3dff3a1e0f5815cf68186870ede8
Tx public key: cf0e501ce1ad265596ef2bd9385e423eef8d890d69096937017c31b2f9770dc5
Timestamp: 1700416948 Timestamp [UCT]: 2023-11-19 18:02:28 Age [y:d:h:m:s]: 01:102:03:56:08
Block: 895200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334164 RingCT/type: yes/0
Extra: 01cf0e501ce1ad265596ef2bd9385e423eef8d890d69096937017c31b2f9770dc502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.663484490000 dcy

stealth address amount amount idx
00: c2c8ab046a654cd3b6432669561848c09c3592a3e010688c0de736beb867c137 0.663484490000 1351423 of 0

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": 895210, "vin": [ { "gen": { "height": 895200 } } ], "vout": [ { "amount": 663484490, "target": { "key": "c2c8ab046a654cd3b6432669561848c09c3592a3e010688c0de736beb867c137" } } ], "extra": [ 1, 207, 14, 80, 28, 225, 173, 38, 85, 150, 239, 43, 217, 56, 94, 66, 62, 239, 141, 137, 13, 105, 9, 105, 55, 1, 124, 49, 178, 249, 119, 13, 197, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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