Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6787e52d1d06c8e5ff5d7f7b599dee2f8944e722b5f3d4d5fb0dd86bc91c3db5

Tx prefix hash: 8b6a1f22eeed7c325c70cd99ba405e2052651dea5004c72ff23ab0f286935ef3
Tx public key: 680477cb7ecf7a2060d092d5f6eff07f1ce0c2e7f02703c68e9ba7f44d1d5087
Timestamp: 1731830349 Timestamp [UCT]: 2024-11-17 07:59:09 Age [y:d:h:m:s]: 00:007:00:12:03
Block: 1155531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5027 RingCT/type: yes/0
Extra: 01680477cb7ecf7a2060d092d5f6eff07f1ce0c2e7f02703c68e9ba7f44d1d5087021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e0df599e167d98b3d8e5e290157d328cf10636a79257a66871adbdeaf29f172 0.600000000000 1641148 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": 1155541, "vin": [ { "gen": { "height": 1155531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e0df599e167d98b3d8e5e290157d328cf10636a79257a66871adbdeaf29f172" } } ], "extra": [ 1, 104, 4, 119, 203, 126, 207, 122, 32, 96, 208, 146, 213, 246, 239, 240, 127, 28, 224, 194, 231, 240, 39, 3, 198, 142, 155, 167, 244, 77, 29, 80, 135, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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