Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 566cf42d8602e3fcf4a5250c40247e1b17e9ecf9b56dad1bcee727209c434ed4

Tx prefix hash: 42190c90fe6be601e43c123dfc74e815c81ce1996ed9c62c6abe56b8c069972b
Tx public key: d6d4d6fd74ca931ef0077153d6b8f63a18087b940bf3d84fc6e533af84d3735e
Timestamp: 1632994030 Timestamp [UCT]: 2021-09-30 09:27:10 Age [y:d:h:m:s]: 03:131:16:29:27
Block: 343662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870816 RingCT/type: yes/0
Extra: 01d6d4d6fd74ca931ef0077153d6b8f63a18087b940bf3d84fc6e533af84d3735e021100000002a272b9cb000000000000000000

1 output(s) for total of 44.596991516000 dcy

stealth address amount amount idx
00: bd93883e5e6e7edf3a18f8aa69bba9adb21fd83641c1cfb0b624c724e8aac890 44.596991516000 705369 of 0

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": 343672, "vin": [ { "gen": { "height": 343662 } } ], "vout": [ { "amount": 44596991516, "target": { "key": "bd93883e5e6e7edf3a18f8aa69bba9adb21fd83641c1cfb0b624c724e8aac890" } } ], "extra": [ 1, 214, 212, 214, 253, 116, 202, 147, 30, 240, 7, 113, 83, 214, 184, 246, 58, 24, 8, 123, 148, 11, 243, 216, 79, 198, 229, 51, 175, 132, 211, 115, 94, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 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