Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 994fba277ee2d251bdd0022a568f2bd3db90368c1f639b16eb3b098dc06f7cbf

Tx prefix hash: 067bc6ffc9d2d50fc9ad3df74a1df07b905059c4f7786c8d34fbb0fddb64d9c2
Tx public key: c7c7c3e8ed4ebbdfa33f3a3e23453856d0af8d4a0b404bd620600bf9d71d39d6
Timestamp: 1744209054 Timestamp [UCT]: 2025-04-09 14:30:54 Age [y:d:h:m:s]: 00:225:17:13:40
Block: 1257758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159041 RingCT/type: yes/0
Extra: 01c7c7c3e8ed4ebbdfa33f3a3e23453856d0af8d4a0b404bd620600bf9d71d39d6021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f675476c3f4ead3cb162dd4e6056af3d18eee609784ca5ebb8b0333731ec2ebc 0.600000000000 1744887 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": 1257768, "vin": [ { "gen": { "height": 1257758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f675476c3f4ead3cb162dd4e6056af3d18eee609784ca5ebb8b0333731ec2ebc" } } ], "extra": [ 1, 199, 199, 195, 232, 237, 78, 187, 223, 163, 63, 58, 62, 35, 69, 56, 86, 208, 175, 141, 74, 11, 64, 75, 214, 32, 96, 11, 249, 215, 29, 57, 214, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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