Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1b42a90be1856f0754a8a3b07f1b0cfbde06783c515e886ca88131def915db3

Tx prefix hash: 812bfe6bfde182047660af312adb33d6da6988063926fa96e8c1449c39df6f21
Tx public key: 00ec64e5fd67e4b503fbf105d1b3d93cdb7f1534e7b43749ab3161fa55ccb3b4
Timestamp: 1702847255 Timestamp [UCT]: 2023-12-17 21:07:35 Age [y:d:h:m:s]: 01:183:09:47:46
Block: 915353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392138 RingCT/type: yes/0
Extra: 0100ec64e5fd67e4b503fbf105d1b3d93cdb7f1534e7b43749ab3161fa55ccb3b402110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aacfe4ced8ee4eb0754dbd5ee7bdfa0237f93a82c4088dcf5b795ff37a21ef79 0.600000000000 1372747 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": 915363, "vin": [ { "gen": { "height": 915353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aacfe4ced8ee4eb0754dbd5ee7bdfa0237f93a82c4088dcf5b795ff37a21ef79" } } ], "extra": [ 1, 0, 236, 100, 229, 253, 103, 228, 181, 3, 251, 241, 5, 209, 179, 217, 60, 219, 127, 21, 52, 231, 180, 55, 73, 171, 49, 97, 250, 85, 204, 179, 180, 2, 17, 0, 0, 0, 14, 117, 227, 240, 233, 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