Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1dd8976f5c1058a6bbb2676e0cf4b430f3023ce77335006ed9ec1556052b90c

Tx prefix hash: 174544bd53a02f9caa15e6ac8ae62bbd873fd1e41c7aee0cc76fb21684ce864a
Tx public key: 0d0660df2f8a77088b52003b045f0503d85175b2fb155abc5ad2600b85f71d64
Timestamp: 1716566426 Timestamp [UCT]: 2024-05-24 16:00:26 Age [y:d:h:m:s]: 00:314:20:25:34
Block: 1029093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225028 RingCT/type: yes/0
Extra: 010d0660df2f8a77088b52003b045f0503d85175b2fb155abc5ad2600b85f71d640211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 793cd5068fd114f2bd6cec4bf0b23e45b7b955460c7a4af767c97e7aab877b86 0.600000000000 1497098 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": 1029103, "vin": [ { "gen": { "height": 1029093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "793cd5068fd114f2bd6cec4bf0b23e45b7b955460c7a4af767c97e7aab877b86" } } ], "extra": [ 1, 13, 6, 96, 223, 47, 138, 119, 8, 139, 82, 0, 59, 4, 95, 5, 3, 216, 81, 117, 178, 251, 21, 90, 188, 90, 210, 96, 11, 133, 247, 29, 100, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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