Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798e5f6edabb4b82b7f7356d38fa1b5a4ebf545304b364e9c79af83fad5d89bf

Tx prefix hash: 3a5d0cb7552cc26f0426ca6e4b11c491cc3464ad0255e8ca6d118718b293d6a8
Tx public key: d2fafd5483a582fe17cb8eee554fa6a5a2a44fbbd1dba2aebab1a44a706f1ec4
Timestamp: 1722543370 Timestamp [UCT]: 2024-08-01 20:16:10 Age [y:d:h:m:s]: 00:234:03:48:32
Block: 1078632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167245 RingCT/type: yes/0
Extra: 01d2fafd5483a582fe17cb8eee554fa6a5a2a44fbbd1dba2aebab1a44a706f1ec4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b61d15f272d18489a7fb2cd8cfa66e8fecab41c9162b6c4e24b369459fbe876 0.600000000000 1551245 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": 1078642, "vin": [ { "gen": { "height": 1078632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b61d15f272d18489a7fb2cd8cfa66e8fecab41c9162b6c4e24b369459fbe876" } } ], "extra": [ 1, 210, 250, 253, 84, 131, 165, 130, 254, 23, 203, 142, 238, 85, 79, 166, 165, 162, 164, 79, 187, 209, 219, 162, 174, 186, 177, 164, 74, 112, 111, 30, 196, 2, 17, 0, 0, 0, 3, 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