Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 116f2b2a9c2d268548a94da6129d679df53b3b71c5f513c2eba61c5bc6a67b0e

Tx prefix hash: 7641be635595868b5f56a31a98065fc852adb4d38bbd1dbe48993d593a0c821a
Tx public key: 98f83559aa6241a6a75b227b6b753fc4f0bdfa14527d7f18794c5110888ac3ec
Timestamp: 1703758587 Timestamp [UCT]: 2023-12-28 10:16:27 Age [y:d:h:m:s]: 01:099:03:42:28
Block: 922901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331980 RingCT/type: yes/0
Extra: 0198f83559aa6241a6a75b227b6b753fc4f0bdfa14527d7f18794c5110888ac3ec0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd6bc49334f6bb0bd572fbfb0d7e760dd7aa5616700ddc851e9ec3f4e5f5011 0.600000000000 1380607 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": 922911, "vin": [ { "gen": { "height": 922901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd6bc49334f6bb0bd572fbfb0d7e760dd7aa5616700ddc851e9ec3f4e5f5011" } } ], "extra": [ 1, 152, 248, 53, 89, 170, 98, 65, 166, 167, 91, 34, 123, 107, 117, 63, 196, 240, 189, 250, 20, 82, 125, 127, 24, 121, 76, 81, 16, 136, 138, 195, 236, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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