Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f23a2f1b13cde37477dd196086b44a749588077607500996d7edbf49b2cb0d61

Tx prefix hash: 7c88a846d3af2ac7c8be2adf2ccba0c6e9303dc01e76ef5a99d5a9314d5e0dfa
Tx public key: 8fb88dd11e096db797b5ba1b673d750f25bd39b60577ab1698acc17a65f4c41b
Timestamp: 1714030532 Timestamp [UCT]: 2024-04-25 07:35:32 Age [y:d:h:m:s]: 00:305:23:30:58
Block: 1008061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218707 RingCT/type: yes/0
Extra: 018fb88dd11e096db797b5ba1b673d750f25bd39b60577ab1698acc17a65f4c41b0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 999ae33dbbdc44e767d0a324ee43889d91e687dfe8dca0b3b12810d6daad5fb2 0.600000000000 1469527 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": 1008071, "vin": [ { "gen": { "height": 1008061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "999ae33dbbdc44e767d0a324ee43889d91e687dfe8dca0b3b12810d6daad5fb2" } } ], "extra": [ 1, 143, 184, 141, 209, 30, 9, 109, 183, 151, 181, 186, 27, 103, 61, 117, 15, 37, 189, 57, 182, 5, 119, 171, 22, 152, 172, 193, 122, 101, 244, 196, 27, 2, 17, 0, 0, 0, 6, 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