Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119cbc9cbdbf99d1d82e6dd05a4c0e33b1f5c8e91206c66b6ed2e2acc668f3b9

Tx prefix hash: e698aeaea73b64d0b4f4e6092b82b071deda7ac9be3e6caa1c11511d6372398b
Tx public key: 0589117971f0e2f44765e29f5cb71e49e7f5a2ee5dd23e0c7a21dcb2a01f5272
Timestamp: 1713211689 Timestamp [UCT]: 2024-04-15 20:08:09 Age [y:d:h:m:s]: 01:025:05:05:39
Block: 1001257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278993 RingCT/type: yes/0
Extra: 010589117971f0e2f44765e29f5cb71e49e7f5a2ee5dd23e0c7a21dcb2a01f527202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 961b3d37ebb8839c1967ef4322504ea4a0f640a473eae4200bf80e73b4ea464d 0.600000000000 1461761 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": 1001267, "vin": [ { "gen": { "height": 1001257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "961b3d37ebb8839c1967ef4322504ea4a0f640a473eae4200bf80e73b4ea464d" } } ], "extra": [ 1, 5, 137, 17, 121, 113, 240, 226, 244, 71, 101, 226, 159, 92, 183, 30, 73, 231, 245, 162, 238, 93, 210, 62, 12, 122, 33, 220, 178, 160, 31, 82, 114, 2, 17, 0, 0, 0, 1, 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