Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574565686f538953fb7a4cd0fc9a34b382482f2985a4e0cd21c71ff21be000d5

Tx prefix hash: 23ad0f603b6307f5d155c2d4e13948631662da30b52d9cc05aaaf8579d21f6da
Tx public key: 77c07c199813f3d5cfd8eb57803e06e3bb3ee88f8f5976f02719a03e506a5dd1
Timestamp: 1676217103 Timestamp [UCT]: 2023-02-12 15:51:43 Age [y:d:h:m:s]: 02:051:07:29:00
Block: 695463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558266 RingCT/type: yes/0
Extra: 0177c07c199813f3d5cfd8eb57803e06e3bb3ee88f8f5976f02719a03e506a5dd10211000000015029cbac000000000000000000

1 output(s) for total of 3.045385675000 dcy

stealth address amount amount idx
00: 1e29eebcd0e60fd4a10e56c40ba23eeb22688ea1b6f326867c9592f39f172241 3.045385675000 1138418 of 0

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": 695473, "vin": [ { "gen": { "height": 695463 } } ], "vout": [ { "amount": 3045385675, "target": { "key": "1e29eebcd0e60fd4a10e56c40ba23eeb22688ea1b6f326867c9592f39f172241" } } ], "extra": [ 1, 119, 192, 124, 25, 152, 19, 243, 213, 207, 216, 235, 87, 128, 62, 6, 227, 187, 62, 232, 143, 143, 89, 118, 240, 39, 25, 160, 62, 80, 106, 93, 209, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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