Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e04e498a4c3041734483ec9da2d467f74f4ce1d8da9d87eae736d860c245c3eb

Tx prefix hash: a7b6a2ea9bdf1a65135c135ec0cd6dcc6295596d9b4739c8354badbeba522784
Tx public key: a845ee4697e8c0bb4126973f89cd6bcc768cf6f7a6796e950bce3afd50097d7c
Timestamp: 1699499571 Timestamp [UCT]: 2023-11-09 03:12:51 Age [y:d:h:m:s]: 01:138:08:07:45
Block: 887598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360036 RingCT/type: yes/0
Extra: 01a845ee4697e8c0bb4126973f89cd6bcc768cf6f7a6796e950bce3afd50097d7c021100000002679a8a81000000000000000000

1 output(s) for total of 0.703103675000 dcy

stealth address amount amount idx
00: 75943e355f4d1109056f306c5b31ccde2f769382cc40d16307c176f871269a11 0.703103675000 1343485 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": 887608, "vin": [ { "gen": { "height": 887598 } } ], "vout": [ { "amount": 703103675, "target": { "key": "75943e355f4d1109056f306c5b31ccde2f769382cc40d16307c176f871269a11" } } ], "extra": [ 1, 168, 69, 238, 70, 151, 232, 192, 187, 65, 38, 151, 63, 137, 205, 107, 204, 118, 140, 246, 247, 166, 121, 110, 149, 11, 206, 58, 253, 80, 9, 125, 124, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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