Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08783cec384a193981e745f76c314246b02dc6ab13190d4e1a9d352a747c4342

Tx prefix hash: fb289f219457ac6e0530db63d6dc833474b7c4fdad1d543c2205527f336c6996
Tx public key: 249356006ab71ea3ee7c7b7f3cda77ea6b3fcfdbae289ea18be10b575c8a44e7
Timestamp: 1709121116 Timestamp [UCT]: 2024-02-28 11:51:56 Age [y:d:h:m:s]: 01:108:18:00:05
Block: 967370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338676 RingCT/type: yes/0
Extra: 01249356006ab71ea3ee7c7b7f3cda77ea6b3fcfdbae289ea18be10b575c8a44e702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d80a49747e1c0ca82fddae7a857a45943516c8c0ee265a96ca07ccc0011c7ec3 0.600000000000 1427147 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": 967380, "vin": [ { "gen": { "height": 967370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d80a49747e1c0ca82fddae7a857a45943516c8c0ee265a96ca07ccc0011c7ec3" } } ], "extra": [ 1, 36, 147, 86, 0, 106, 183, 30, 163, 238, 124, 123, 127, 60, 218, 119, 234, 107, 63, 207, 219, 174, 40, 158, 161, 139, 225, 11, 87, 92, 138, 68, 231, 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