Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac7605443ac2e89e33bb14b99c8a13aedac365e3f403c14ae1e6f463eef84f42

Tx prefix hash: 558216fdf2aa1071fa724d76e37822987a322c7a0ddef64892a5a69776695ac4
Tx public key: a19a99eb6a68a2b91116f8bb5bf5401976f13c5229dc529b2beaa7b7e58f4173
Timestamp: 1712554047 Timestamp [UCT]: 2024-04-08 05:27:27 Age [y:d:h:m:s]: 01:067:14:49:09
Block: 995792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309266 RingCT/type: yes/0
Extra: 01a19a99eb6a68a2b91116f8bb5bf5401976f13c5229dc529b2beaa7b7e58f41730211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35dd4be7ccf81f6329ee230720bb2cd166d4a3731a0b02924ce9125efee4cf27 0.600000000000 1456206 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": 995802, "vin": [ { "gen": { "height": 995792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35dd4be7ccf81f6329ee230720bb2cd166d4a3731a0b02924ce9125efee4cf27" } } ], "extra": [ 1, 161, 154, 153, 235, 106, 104, 162, 185, 17, 22, 248, 187, 91, 245, 64, 25, 118, 241, 60, 82, 41, 220, 82, 155, 43, 234, 167, 183, 229, 143, 65, 115, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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