Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 751bfd5980b38708b98ddb3f422142097c73d97fdc942712ce6a9e53e2c1d53a

Tx prefix hash: c13ad17a4df985222f46c06f54647fe79fceb3bdc5a41f5dd75d635fe595f882
Tx public key: aee5f44deef4ea1ed77123d020afed7821ae25b22072ae5fa8a1e335a4828731
Timestamp: 1724640913 Timestamp [UCT]: 2024-08-26 02:55:13 Age [y:d:h:m:s]: 00:296:20:42:38
Block: 1096028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211946 RingCT/type: yes/0
Extra: 01aee5f44deef4ea1ed77123d020afed7821ae25b22072ae5fa8a1e335a482873102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b9a3816ca5a133e946b492bdac9ee860a179fc08c1dc7eadae2dae7b1b5b43a 0.600000000000 1571215 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": 1096038, "vin": [ { "gen": { "height": 1096028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b9a3816ca5a133e946b492bdac9ee860a179fc08c1dc7eadae2dae7b1b5b43a" } } ], "extra": [ 1, 174, 229, 244, 77, 238, 244, 234, 30, 215, 113, 35, 208, 32, 175, 237, 120, 33, 174, 37, 178, 32, 114, 174, 95, 168, 161, 227, 53, 164, 130, 135, 49, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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