Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3adc60f1c9f08b3822bf2cea22841a5be393b09a4427f1155897993d9df2f1d

Tx prefix hash: d85c47f939d3cd222a8780c0eadc5564d3744a09978eb05c8355cc620651396c
Tx public key: fbe97c7899aa85017d29398e2ade178e0bf7bea33acd460475a7af04002dbaa0
Timestamp: 1706963654 Timestamp [UCT]: 2024-02-03 12:34:14 Age [y:d:h:m:s]: 01:064:19:27:53
Block: 949468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307378 RingCT/type: yes/0
Extra: 01fbe97c7899aa85017d29398e2ade178e0bf7bea33acd460475a7af04002dbaa00211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32a8e16cb9ef61e7cf713cb5f55de7dbd24a736e9e07baf8b4d6a8d4da72af7d 0.600000000000 1407994 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": 949478, "vin": [ { "gen": { "height": 949468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32a8e16cb9ef61e7cf713cb5f55de7dbd24a736e9e07baf8b4d6a8d4da72af7d" } } ], "extra": [ 1, 251, 233, 124, 120, 153, 170, 133, 1, 125, 41, 57, 142, 42, 222, 23, 142, 11, 247, 190, 163, 58, 205, 70, 4, 117, 167, 175, 4, 0, 45, 186, 160, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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