Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78b3be69d7c5752a36a2428743a9228756fd5294cab9b143e98d3a91873dbab7

Tx prefix hash: 85ac706a6df56b85a664fd484642b2be482128506af9a0b20ea4d8a6d565ac69
Tx public key: 459e58a6d3cdbfd16130e4ad09e55bab95b987921e62f546a44056e5ffbdfb25
Timestamp: 1706560379 Timestamp [UCT]: 2024-01-29 20:32:59 Age [y:d:h:m:s]: 01:071:11:55:52
Block: 946115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312180 RingCT/type: yes/0
Extra: 01459e58a6d3cdbfd16130e4ad09e55bab95b987921e62f546a44056e5ffbdfb2502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a1c59d7292b40cbd7fc3d28bf8685e8039c1de8e4a52dca3ff6d6592c0a3dcf 0.600000000000 1404445 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": 946125, "vin": [ { "gen": { "height": 946115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a1c59d7292b40cbd7fc3d28bf8685e8039c1de8e4a52dca3ff6d6592c0a3dcf" } } ], "extra": [ 1, 69, 158, 88, 166, 211, 205, 191, 209, 97, 48, 228, 173, 9, 229, 91, 171, 149, 185, 135, 146, 30, 98, 245, 70, 164, 64, 86, 229, 255, 189, 251, 37, 2, 17, 0, 0, 0, 5, 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