Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c95f059d13bbe84498d2c711e4b19690a65f91fd3fe8c9735eb62e6b9a00ee

Tx prefix hash: 8502785542d3c64f629fd6b2061f92d165b736ad3b48d04172908b133ff0f452
Tx public key: 351703e54385f8f7c8266da5303e4fa890198e03a364d7d6cd3c468d2e351a74
Timestamp: 1729011068 Timestamp [UCT]: 2024-10-15 16:51:08 Age [y:d:h:m:s]: 00:175:08:55:50
Block: 1132263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125117 RingCT/type: yes/0
Extra: 01351703e54385f8f7c8266da5303e4fa890198e03a364d7d6cd3c468d2e351a74021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d762cc046acb12d77438eea3d583b665437a2b95aad3e1afb4a511296bd1b0 0.600000000000 1615176 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": 1132273, "vin": [ { "gen": { "height": 1132263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d762cc046acb12d77438eea3d583b665437a2b95aad3e1afb4a511296bd1b0" } } ], "extra": [ 1, 53, 23, 3, 229, 67, 133, 248, 247, 200, 38, 109, 165, 48, 62, 79, 168, 144, 25, 142, 3, 163, 100, 215, 214, 205, 60, 70, 141, 46, 53, 26, 116, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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