Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832cf7f69d21dee5e11f3c05f2aa79c706aa25340bd7a8b93fc5be0cb89d56e2

Tx prefix hash: 6d8c0f74e94fa85f0b44fb0b4ad06ef85429927418ace51f15a6fae4e65c7a72
Tx public key: b3443c37fba1e5e4998eb10262b41a37ad6ed9004e09f3320fb78a4a047e5d64
Timestamp: 1712023710 Timestamp [UCT]: 2024-04-02 02:08:30 Age [y:d:h:m:s]: 01:016:00:46:29
Block: 991394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272455 RingCT/type: yes/0
Extra: 01b3443c37fba1e5e4998eb10262b41a37ad6ed9004e09f3320fb78a4a047e5d6402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dcba18e8bece2d4d262b9e638f9bf96fb41a8e907ef0c8a9bb550e06b294293 0.600000000000 1451728 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": 991404, "vin": [ { "gen": { "height": 991394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dcba18e8bece2d4d262b9e638f9bf96fb41a8e907ef0c8a9bb550e06b294293" } } ], "extra": [ 1, 179, 68, 60, 55, 251, 161, 229, 228, 153, 142, 177, 2, 98, 180, 26, 55, 173, 110, 217, 0, 78, 9, 243, 50, 15, 183, 138, 74, 4, 126, 93, 100, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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