Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c85072a5ae86876ffb8285db0d514403c503cfd007e89ff416c19cee5a2dcaab

Tx prefix hash: 6f31eec4694f1e58b7f468cdc3ab5716d5927796d34babe21dd2957d9d7f1c40
Tx public key: 4a404cb82dc7ca90657f56640053553a0d8e9009b3a02a0a620c5f4e1d9aade2
Timestamp: 1727544555 Timestamp [UCT]: 2024-09-28 17:29:15 Age [y:d:h:m:s]: 00:024:13:58:26
Block: 1120112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17567 RingCT/type: yes/0
Extra: 014a404cb82dc7ca90657f56640053553a0d8e9009b3a02a0a620c5f4e1d9aade2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b67eb1b8e05aa32b6ac6cc5b45dbffbaee4f696e18af5fd2c9dd8d0ca7a7ad64 0.600000000000 1601909 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": 1120122, "vin": [ { "gen": { "height": 1120112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67eb1b8e05aa32b6ac6cc5b45dbffbaee4f696e18af5fd2c9dd8d0ca7a7ad64" } } ], "extra": [ 1, 74, 64, 76, 184, 45, 199, 202, 144, 101, 127, 86, 100, 0, 83, 85, 58, 13, 142, 144, 9, 179, 160, 42, 10, 98, 12, 95, 78, 29, 154, 173, 226, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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