Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1266835a984c1f58ef9d84992de4351a34300bbf8d49eeec023902bbfc7539

Tx prefix hash: 3fe34894dd4f220353b8f6b9fc2eb5fd4d113127621e502f683b8ca921f7b4ae
Tx public key: b0c1543ad6ace88f4c4bbda1d4e4f84cf46a904e38db0e6c4301ad6a3e499f58
Timestamp: 1711437843 Timestamp [UCT]: 2024-03-26 07:24:03 Age [y:d:h:m:s]: 01:051:05:05:18
Block: 986591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297574 RingCT/type: yes/0
Extra: 01b0c1543ad6ace88f4c4bbda1d4e4f84cf46a904e38db0e6c4301ad6a3e499f580211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f44ae2a5534015294469f7ecde67aa2ed4ca64133c66bd350db9a207245070f 0.600000000000 1446822 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": 986601, "vin": [ { "gen": { "height": 986591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f44ae2a5534015294469f7ecde67aa2ed4ca64133c66bd350db9a207245070f" } } ], "extra": [ 1, 176, 193, 84, 58, 214, 172, 232, 143, 76, 75, 189, 161, 212, 228, 248, 76, 244, 106, 144, 78, 56, 219, 14, 108, 67, 1, 173, 106, 62, 73, 159, 88, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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