Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e80f20acc68f63f3af99c4bf463283ee2484ce668f731d7b2b016a3037969a2

Tx prefix hash: 98c9759c942c41328475d4f1e5069f789eab9d6efded043dcbbed323d84d763e
Tx public key: 763f76ff273f02021a294a1338d4d88e31636ba3056b23e1a811e6067d6dbe65
Timestamp: 1703950501 Timestamp [UCT]: 2023-12-30 15:35:01 Age [y:d:h:m:s]: 01:091:22:08:34
Block: 924496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326801 RingCT/type: yes/0
Extra: 01763f76ff273f02021a294a1338d4d88e31636ba3056b23e1a811e6067d6dbe650211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 589779fddf293fa788ce2f95ef0b5d4dc75147461d7368c424e3b03ba1061f6f 0.600000000000 1382250 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": 924506, "vin": [ { "gen": { "height": 924496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "589779fddf293fa788ce2f95ef0b5d4dc75147461d7368c424e3b03ba1061f6f" } } ], "extra": [ 1, 118, 63, 118, 255, 39, 63, 2, 2, 26, 41, 74, 19, 56, 212, 216, 142, 49, 99, 107, 163, 5, 107, 35, 225, 168, 17, 230, 6, 125, 109, 190, 101, 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