Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07749ac68115af4b70c4252c4fb3834a0043292f4aadf8d9ad98e25ecb65e57a

Tx prefix hash: 7a549932593e306aef1fac981d33fc1043405646f880e928579ee91712725ed8
Tx public key: cd71b48eea392d4db6bd4b181b7191aa361812a28a1c1e41761f9545ae2c6ffd
Timestamp: 1574751690 Timestamp [UCT]: 2019-11-26 07:01:30 Age [y:d:h:m:s]: 05:140:07:25:44
Block: 17710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1242909 RingCT/type: yes/0
Extra: 01cd71b48eea392d4db6bd4b181b7191aa361812a28a1c1e41761f9545ae2c6ffd0211000000015ce78bfa000000000000000000

1 output(s) for total of 536.191960992000 dcy

stealth address amount amount idx
00: b2527365b047f53a79d22590e8a080bc798f06d680eda75f9c2f51d961cab665 536.191960992000 26148 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": 17720, "vin": [ { "gen": { "height": 17710 } } ], "vout": [ { "amount": 536191960992, "target": { "key": "b2527365b047f53a79d22590e8a080bc798f06d680eda75f9c2f51d961cab665" } } ], "extra": [ 1, 205, 113, 180, 142, 234, 57, 45, 77, 182, 189, 75, 24, 27, 113, 145, 170, 54, 24, 18, 162, 138, 28, 30, 65, 118, 31, 149, 69, 174, 44, 111, 253, 2, 17, 0, 0, 0, 1, 92, 231, 139, 250, 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