Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c557fc8f9b6268e8f1ca5c8579c0e2e7b786983117378c0ee0acac1405facaa4

Tx prefix hash: 408044efb763273821f316d851de9369cfeac77f0e91de063e589bcdc9f4fb33
Tx public key: 481bb6f7d98be8ef489251100304b900df83b862599ee28dcad64e8cb271c582
Timestamp: 1709939070 Timestamp [UCT]: 2024-03-08 23:04:30 Age [y:d:h:m:s]: 01:243:05:55:46
Block: 974152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432554 RingCT/type: yes/0
Extra: 01481bb6f7d98be8ef489251100304b900df83b862599ee28dcad64e8cb271c5820211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ace9b41df13826a0c46c63496033655db93082fdd03dbe5e98563a96e2e4f8ae 0.600000000000 1434103 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": 974162, "vin": [ { "gen": { "height": 974152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ace9b41df13826a0c46c63496033655db93082fdd03dbe5e98563a96e2e4f8ae" } } ], "extra": [ 1, 72, 27, 182, 247, 217, 139, 232, 239, 72, 146, 81, 16, 3, 4, 185, 0, 223, 131, 184, 98, 89, 158, 226, 141, 202, 214, 78, 140, 178, 113, 197, 130, 2, 17, 0, 0, 0, 7, 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