Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2379fef8356d5c2cd8fb63fe9833908906d22d2a3ea5bda1745ce77115a114

Tx prefix hash: cfb1b7f2f4f34ed43d69c97c39c944b1d6e7917d412a87ff4ebef374150f79b4
Tx public key: 4ad384a52798f4f2741e7ba555f12f1482d0beacb8ca77d06d9a7e01f8a0d69d
Timestamp: 1674070442 Timestamp [UCT]: 2023-01-18 19:34:02 Age [y:d:h:m:s]: 02:000:14:24:22
Block: 677636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522319 RingCT/type: yes/0
Extra: 014ad384a52798f4f2741e7ba555f12f1482d0beacb8ca77d06d9a7e01f8a0d69d02110000000152542ceb000000000000000000

1 output(s) for total of 3.489077193000 dcy

stealth address amount amount idx
00: 61df5a4c0725429ec0cbbb5d1173a17d0d22ff1699659a5376f6b3d4e63ea83b 3.489077193000 1119425 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": 677646, "vin": [ { "gen": { "height": 677636 } } ], "vout": [ { "amount": 3489077193, "target": { "key": "61df5a4c0725429ec0cbbb5d1173a17d0d22ff1699659a5376f6b3d4e63ea83b" } } ], "extra": [ 1, 74, 211, 132, 165, 39, 152, 244, 242, 116, 30, 123, 165, 85, 241, 47, 20, 130, 208, 190, 172, 184, 202, 119, 208, 109, 154, 126, 1, 248, 160, 214, 157, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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