Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8512a4db6531bbe9a475c5f9524a772d6baab658ec4ed4cac8fd961630cc9dd4

Tx prefix hash: 717ac10d0d859f6b5a87718e062f1b672ca011f83e0563202ab40da9a39ebc16
Tx public key: 1434bd75a829108475f894c2cdee6122a7849f32a6cf67702ff788f9f44b0e40
Timestamp: 1716326707 Timestamp [UCT]: 2024-05-21 21:25:07 Age [y:d:h:m:s]: 00:278:00:53:35
Block: 1027103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198692 RingCT/type: yes/0
Extra: 011434bd75a829108475f894c2cdee6122a7849f32a6cf67702ff788f9f44b0e4002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 576b79b3c8f55c5c1cb26adb0fa2d29968c7d31d3ec4c1d19e8816eda56fa068 0.600000000000 1494550 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": 1027113, "vin": [ { "gen": { "height": 1027103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "576b79b3c8f55c5c1cb26adb0fa2d29968c7d31d3ec4c1d19e8816eda56fa068" } } ], "extra": [ 1, 20, 52, 189, 117, 168, 41, 16, 132, 117, 248, 148, 194, 205, 238, 97, 34, 167, 132, 159, 50, 166, 207, 103, 112, 47, 247, 136, 249, 244, 75, 14, 64, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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