Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a979927232ed2b32423f6e0526b3c34d8b1015cb372a8ee440300b57cdcaf99

Tx prefix hash: 2d1b5dd2d9342d13c58860ad64d311fb0029a0e84dcd78209ef0aa6e9431fc87
Tx public key: 6371873e1b2d089af08865497404f249bd32704f40594ed728d9196b7e366b11
Timestamp: 1733954078 Timestamp [UCT]: 2024-12-11 21:54:38 Age [y:d:h:m:s]: 00:108:09:16:00
Block: 1173153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77232 RingCT/type: yes/0
Extra: 016371873e1b2d089af08865497404f249bd32704f40594ed728d9196b7e366b11021100000004c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cac089eff2e25d1571f9a41ce441d9d4b46106b0111b1625f7d3d3855ce3dfc 0.600000000000 1659142 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": 1173163, "vin": [ { "gen": { "height": 1173153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cac089eff2e25d1571f9a41ce441d9d4b46106b0111b1625f7d3d3855ce3dfc" } } ], "extra": [ 1, 99, 113, 135, 62, 27, 45, 8, 154, 240, 136, 101, 73, 116, 4, 242, 73, 189, 50, 112, 79, 64, 89, 78, 215, 40, 217, 25, 107, 126, 54, 107, 17, 2, 17, 0, 0, 0, 4, 199, 202, 20, 193, 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