Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81a609aad9223c1290f81061c1524358b77a4b4d1bd07b8e8f6091a44ce27f89

Tx prefix hash: bf4334f9fc35b83ddd770efead48646583b4d55735e3379ccf9ec78ddd758347
Tx public key: be04c43aa60be5ea6d963d0f6b0fcb815eecb57b2a4b53135acebdb359c75d76
Timestamp: 1703263548 Timestamp [UCT]: 2023-12-22 16:45:48 Age [y:d:h:m:s]: 01:145:06:03:13
Block: 918804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364946 RingCT/type: yes/0
Extra: 01be04c43aa60be5ea6d963d0f6b0fcb815eecb57b2a4b53135acebdb359c75d7602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff0e6b5170c32f0d1d60fbe6afcdd7e764914699040ded735d4f1901a7f622da 0.600000000000 1376462 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": 918814, "vin": [ { "gen": { "height": 918804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff0e6b5170c32f0d1d60fbe6afcdd7e764914699040ded735d4f1901a7f622da" } } ], "extra": [ 1, 190, 4, 196, 58, 166, 11, 229, 234, 109, 150, 61, 15, 107, 15, 203, 129, 94, 236, 181, 123, 42, 75, 83, 19, 90, 206, 189, 179, 89, 199, 93, 118, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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