Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 077cbe4c4421c6956471b9d9836c8b529ea59bd1bc2617396999d6330f4b6359

Tx prefix hash: 9853014f1d0e915f6d2bc231ca2db941f939639533dc8f070fdb6978b23a2869
Tx public key: b91ebb101e8e578c34348a4dbc4bc02f8795ae6a01d38fae0e8a552757b5bf03
Timestamp: 1718112514 Timestamp [UCT]: 2024-06-11 13:28:34 Age [y:d:h:m:s]: 01:003:23:26:06
Block: 1041918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263623 RingCT/type: yes/0
Extra: 01b91ebb101e8e578c34348a4dbc4bc02f8795ae6a01d38fae0e8a552757b5bf030211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77943d947178a3de74145e46d63e9cee1d5ded34cebdbc53c685999fd8ae3f2e 0.600000000000 1510709 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": 1041928, "vin": [ { "gen": { "height": 1041918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77943d947178a3de74145e46d63e9cee1d5ded34cebdbc53c685999fd8ae3f2e" } } ], "extra": [ 1, 185, 30, 187, 16, 30, 142, 87, 140, 52, 52, 138, 77, 188, 75, 192, 47, 135, 149, 174, 106, 1, 211, 143, 174, 14, 138, 85, 39, 87, 181, 191, 3, 2, 17, 0, 0, 0, 2, 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