Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3652bd45dd87cf906fc05790307f8548efa51814adfc8c6e6c580dd4f90134c8

Tx prefix hash: f0b966e6cb5a2ca4d402c1b48de9bee12b088556483b12405d140867203add17
Tx public key: b69e6f69297871b542976fb4a8b952d0475b59ad3ad847bb5c8719bf322dd039
Timestamp: 1705354304 Timestamp [UCT]: 2024-01-15 21:31:44 Age [y:d:h:m:s]: 01:012:01:26:18
Block: 936117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269794 RingCT/type: yes/0
Extra: 01b69e6f69297871b542976fb4a8b952d0475b59ad3ad847bb5c8719bf322dd0390211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6767629f408d29a4df11a61a31f6a644141d019ccab4f768a733beec25f373e5 0.600000000000 1394139 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": 936127, "vin": [ { "gen": { "height": 936117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6767629f408d29a4df11a61a31f6a644141d019ccab4f768a733beec25f373e5" } } ], "extra": [ 1, 182, 158, 111, 105, 41, 120, 113, 181, 66, 151, 111, 180, 168, 185, 82, 208, 71, 91, 89, 173, 58, 216, 71, 187, 92, 135, 25, 191, 50, 45, 208, 57, 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