Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7fa0c6e4c4de7e1e5904ce877e6751a6daaf05a94664e7b89cd225a6abb9554

Tx prefix hash: 497639a0d3175a576a3f6d47ec4b76ec0f75554540746235361b17892822bd25
Tx public key: 6e58d8c319430209e7d9ded3c7da67a524a444ca742e408bbdf28d75b052d2c1
Timestamp: 1702242732 Timestamp [UCT]: 2023-12-10 21:12:12 Age [y:d:h:m:s]: 01:333:14:11:08
Block: 910340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497269 RingCT/type: yes/0
Extra: 016e58d8c319430209e7d9ded3c7da67a524a444ca742e408bbdf28d75b052d2c1021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39a1033bf5c7cbbb63426a084d8581bd6004d524288da07e25732fb02f14b5f9 0.600000000000 1367491 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": 910350, "vin": [ { "gen": { "height": 910340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39a1033bf5c7cbbb63426a084d8581bd6004d524288da07e25732fb02f14b5f9" } } ], "extra": [ 1, 110, 88, 216, 195, 25, 67, 2, 9, 231, 217, 222, 211, 199, 218, 103, 165, 36, 164, 68, 202, 116, 46, 64, 139, 189, 242, 141, 117, 176, 82, 210, 193, 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