Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eef3d41e8f291d07d34ddd247d963bc76e562af1b593d9b4373346d5352149e

Tx prefix hash: a04fed29885200c26a4d86c4a10f5ec00ec7491fcd5067d855a0e0067fdfda06
Tx public key: 0febe8e0f0930a8439a89a82dda2d748f47505b93e1a88ee13239805a6cf3ca1
Timestamp: 1731412346 Timestamp [UCT]: 2024-11-12 11:52:26 Age [y:d:h:m:s]: 00:139:05:36:29
Block: 1152076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99333 RingCT/type: yes/0
Extra: 010febe8e0f0930a8439a89a82dda2d748f47505b93e1a88ee13239805a6cf3ca1021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09ab2348a5f3bbb550d370d5fe4cdc97cd19322e7ad6391c7e372cc767f8f211 0.600000000000 1637667 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": 1152086, "vin": [ { "gen": { "height": 1152076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09ab2348a5f3bbb550d370d5fe4cdc97cd19322e7ad6391c7e372cc767f8f211" } } ], "extra": [ 1, 15, 235, 232, 224, 240, 147, 10, 132, 57, 168, 154, 130, 221, 162, 215, 72, 244, 117, 5, 185, 62, 26, 136, 238, 19, 35, 152, 5, 166, 207, 60, 161, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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