Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa4af40a067c9858bdd7a0c6c33a105ce0c5044dbbfd367fd0f822205d80409

Tx prefix hash: 297d3b3e5f837fdaa4717801d1932d9912447d11cb4c8ff260223068405b7920
Tx public key: d75e499fd580cc57ab2dc380d198d7d91cb5cd7dfa9afe1c4e8eb68e97af29cf
Timestamp: 1715700131 Timestamp [UCT]: 2024-05-14 15:22:11 Age [y:d:h:m:s]: 01:177:09:16:21
Block: 1021916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385377 RingCT/type: yes/0
Extra: 01d75e499fd580cc57ab2dc380d198d7d91cb5cd7dfa9afe1c4e8eb68e97af29cf021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c20afdea22e669c56e0dbcd5c7a1ff6dc1f5669d88c64341d91da1995af26797 0.600000000000 1486365 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": 1021926, "vin": [ { "gen": { "height": 1021916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c20afdea22e669c56e0dbcd5c7a1ff6dc1f5669d88c64341d91da1995af26797" } } ], "extra": [ 1, 215, 94, 73, 159, 213, 128, 204, 87, 171, 45, 195, 128, 209, 152, 215, 217, 28, 181, 205, 125, 250, 154, 254, 28, 78, 142, 182, 142, 151, 175, 41, 207, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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