Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fc930a2ec601d40f552aff1e8c09dd22acbb5c1357b2f915c986bc7d519b978

Tx prefix hash: 348bcdbe52b35525e9fd7cc36315fb4a02235cd2a0f52cb77b72e3662373162c
Tx public key: 64c7cb3ad70147a3d29db4a7f069d49e3ca6c6ff54fdce730d3fccd9ea8af5ba
Timestamp: 1698130614 Timestamp [UCT]: 2023-10-24 06:56:54 Age [y:d:h:m:s]: 01:162:18:46:05
Block: 876454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377340 RingCT/type: yes/0
Extra: 0164c7cb3ad70147a3d29db4a7f069d49e3ca6c6ff54fdce730d3fccd9ea8af5ba02110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.765498039000 dcy

stealth address amount amount idx
00: 5ff969e2953c4bfc4479ab94c0196c8444c603235fb41a5dfe106a21435e2561 0.765498039000 1331780 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": 876464, "vin": [ { "gen": { "height": 876454 } } ], "vout": [ { "amount": 765498039, "target": { "key": "5ff969e2953c4bfc4479ab94c0196c8444c603235fb41a5dfe106a21435e2561" } } ], "extra": [ 1, 100, 199, 203, 58, 215, 1, 71, 163, 210, 157, 180, 167, 240, 105, 212, 158, 60, 166, 198, 255, 84, 253, 206, 115, 13, 63, 204, 217, 234, 138, 245, 186, 2, 17, 0, 0, 0, 11, 250, 243, 92, 156, 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