Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3af93ecf2193ba3ae5b61ed241daf31ada3cb82bed0da78d85a9f64285bb7979

Tx prefix hash: 6a80158c0e0afc507a795b0f9e5068c45e88f05d14f3f09d1046beaba573f289
Tx public key: 66a556b32c424c86b994d37d91c5e07e1ad35434870623e2e1f71085ed3b25a2
Timestamp: 1703788649 Timestamp [UCT]: 2023-12-28 18:37:29 Age [y:d:h:m:s]: 01:108:15:27:14
Block: 923157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338764 RingCT/type: yes/0
Extra: 0166a556b32c424c86b994d37d91c5e07e1ad35434870623e2e1f71085ed3b25a2021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de9340d4ae0c5bf55b6c348633f9b155cfb21883919c99aceeec09ceb4d9d4ed 0.600000000000 1380883 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": 923167, "vin": [ { "gen": { "height": 923157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de9340d4ae0c5bf55b6c348633f9b155cfb21883919c99aceeec09ceb4d9d4ed" } } ], "extra": [ 1, 102, 165, 86, 179, 44, 66, 76, 134, 185, 148, 211, 125, 145, 197, 224, 126, 26, 211, 84, 52, 135, 6, 35, 226, 225, 247, 16, 133, 237, 59, 37, 162, 2, 17, 0, 0, 0, 1, 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