Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f1051c885a3413fdd025579a46cf8e02f7c231a18dd58f4e6183054463f637a

Tx prefix hash: 41958d3588a67217bff2f35c234264ecc08f4493d0184e187c43cc34b4df044a
Tx public key: d5fae8403ea374157a0297976703a5f9c1ad8377eb38ba91e4805927a833f2df
Timestamp: 1731492702 Timestamp [UCT]: 2024-11-13 10:11:42 Age [y:d:h:m:s]: 00:138:19:13:02
Block: 1152747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99018 RingCT/type: yes/0
Extra: 01d5fae8403ea374157a0297976703a5f9c1ad8377eb38ba91e4805927a833f2df0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac9edf8b727d55b7c6b87e3b2dba9cc12433b8e4dec803d9e1fd8467f802e0f 0.600000000000 1638350 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": 1152757, "vin": [ { "gen": { "height": 1152747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac9edf8b727d55b7c6b87e3b2dba9cc12433b8e4dec803d9e1fd8467f802e0f" } } ], "extra": [ 1, 213, 250, 232, 64, 62, 163, 116, 21, 122, 2, 151, 151, 103, 3, 165, 249, 193, 173, 131, 119, 235, 56, 186, 145, 228, 128, 89, 39, 168, 51, 242, 223, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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