Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cc0c2ec21b7e93a30381e7d6bca6714580e30bfc723d9c096e33982486654af

Tx prefix hash: 2d6068cd8c5efdf446291a9f9dbfb5f14fc59ebd03dea7c35d0a8dc9b2434a5b
Tx public key: ff9a7a873cfc09b15f6504d5477801050de0a4aac27b9b137f306bd722017526
Timestamp: 1736528055 Timestamp [UCT]: 2025-01-10 16:54:15 Age [y:d:h:m:s]: 00:158:16:03:44
Block: 1194432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113115 RingCT/type: yes/0
Extra: 01ff9a7a873cfc09b15f6504d5477801050de0a4aac27b9b137f306bd722017526021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1dfa0afb2af31f42c1ec6951119c40356c6a50b109b29db3697e81650dfa295 0.600000000000 1681003 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": 1194442, "vin": [ { "gen": { "height": 1194432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1dfa0afb2af31f42c1ec6951119c40356c6a50b109b29db3697e81650dfa295" } } ], "extra": [ 1, 255, 154, 122, 135, 60, 252, 9, 177, 95, 101, 4, 213, 71, 120, 1, 5, 13, 224, 164, 170, 194, 123, 155, 19, 127, 48, 107, 215, 34, 1, 117, 38, 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