Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549da61cc25c242f8a69e517d614f9ec78c39337e14d5cdc1c7792dce771264f

Tx prefix hash: 53b1d5cf25bef1ca3e614c450972a6e08a935814452908fe5681cf3b1e6d0c20
Tx public key: 00c8dbc271a45261a8b0cbb329548a88ed1eba5427a8e579eb1212bd282185bb
Timestamp: 1722356155 Timestamp [UCT]: 2024-07-30 16:15:55 Age [y:d:h:m:s]: 00:092:21:14:11
Block: 1077083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66469 RingCT/type: yes/0
Extra: 0100c8dbc271a45261a8b0cbb329548a88ed1eba5427a8e579eb1212bd282185bb021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55943050073eda46d5efa73a9106335d0fd18b36f72074184d79e9d0fc5265ae 0.600000000000 1549626 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": 1077093, "vin": [ { "gen": { "height": 1077083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55943050073eda46d5efa73a9106335d0fd18b36f72074184d79e9d0fc5265ae" } } ], "extra": [ 1, 0, 200, 219, 194, 113, 164, 82, 97, 168, 176, 203, 179, 41, 84, 138, 136, 237, 30, 186, 84, 39, 168, 229, 121, 235, 18, 18, 189, 40, 33, 133, 187, 2, 17, 0, 0, 0, 5, 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