Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a4a1a4698cfd5a7bc6e5a00dfec7814c1cf01a7ec1850e6aeabc42b2732e901

Tx prefix hash: 20714d99eab7a239a3f41075e046f9b8f75faa333b4430152fc0e48b084af08b
Tx public key: 6f731751d9a1d5388f391b0ec1d982a6c7bfd8c70913b184fe4426da784384e9
Timestamp: 1577968126 Timestamp [UCT]: 2020-01-02 12:28:46 Age [y:d:h:m:s]: 04:183:08:32:56
Block: 37215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1019951 RingCT/type: yes/0
Extra: 016f731751d9a1d5388f391b0ec1d982a6c7bfd8c70913b184fe4426da784384e902110000000a4ac5aa02000000000000000000

1 output(s) for total of 462.053333722000 dcy

stealth address amount amount idx
00: 757cd96a5f81d12d177271dc1a1c9fd2533848ec0211e79d3463f4487d424e33 462.053333722000 63099 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": 37225, "vin": [ { "gen": { "height": 37215 } } ], "vout": [ { "amount": 462053333722, "target": { "key": "757cd96a5f81d12d177271dc1a1c9fd2533848ec0211e79d3463f4487d424e33" } } ], "extra": [ 1, 111, 115, 23, 81, 217, 161, 213, 56, 143, 57, 27, 14, 193, 217, 130, 166, 199, 191, 216, 199, 9, 19, 177, 132, 254, 68, 38, 218, 120, 67, 132, 233, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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