Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6b19ce103554b2ce38e0429e38f236fe9ce1f3e24e662f6b055d94ede196d47

Tx prefix hash: d19aa70da5a5c34b995d91b6d0ccfce5732096bd8cd72233edba8d836d2c38a4
Tx public key: 16b0f084036b141177aba3c9f0a2ffd914c03b829bbfe3947c7ba4eb637f8ba4
Timestamp: 1712953203 Timestamp [UCT]: 2024-04-12 20:20:03 Age [y:d:h:m:s]: 01:040:06:04:42
Block: 999114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289775 RingCT/type: yes/0
Extra: 0116b0f084036b141177aba3c9f0a2ffd914c03b829bbfe3947c7ba4eb637f8ba40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c763db78525b7c6452f8a1f900df734eba522c9a901862e328ab27ed37fee95b 0.600000000000 1459592 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": 999124, "vin": [ { "gen": { "height": 999114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c763db78525b7c6452f8a1f900df734eba522c9a901862e328ab27ed37fee95b" } } ], "extra": [ 1, 22, 176, 240, 132, 3, 107, 20, 17, 119, 171, 163, 201, 240, 162, 255, 217, 20, 192, 59, 130, 155, 191, 227, 148, 124, 123, 164, 235, 99, 127, 139, 164, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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