Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5057f9c76bd4b4edd28a35f1a85ff8ff48fcc5c31e74fe1ddc85b6f7baf891e3

Tx prefix hash: 38e734901c65085eb0d6ba0a00899549a00e299815dba04f26b25934af05577c
Tx public key: add1b7f6b28a67758beb8c2453b38cb675b8fa05a7f8c1a83300ee23b754564e
Timestamp: 1704704531 Timestamp [UCT]: 2024-01-08 09:02:11 Age [y:d:h:m:s]: 01:350:18:30:17
Block: 930740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509569 RingCT/type: yes/0
Extra: 01add1b7f6b28a67758beb8c2453b38cb675b8fa05a7f8c1a83300ee23b754564e02110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e89917bafd086a55b4e1909b91031b82f52aac69ee66531e3836d72fa876e8 0.600000000000 1388628 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": 930750, "vin": [ { "gen": { "height": 930740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e89917bafd086a55b4e1909b91031b82f52aac69ee66531e3836d72fa876e8" } } ], "extra": [ 1, 173, 209, 183, 246, 178, 138, 103, 117, 139, 235, 140, 36, 83, 179, 140, 182, 117, 184, 250, 5, 167, 248, 193, 168, 51, 0, 238, 35, 183, 84, 86, 78, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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