Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25093ab415fad595e890cfd3e1dd743de83efac4f09c0fbd2963e14367aba39d

Tx prefix hash: dbae2b3e4780a064ca35792bb235596242698752f3f0190ef5da5174b8f20aad
Tx public key: fb9bd124eaaf01ca0226c46e1d99eedd59268d78a24f95a971e8d9d21d5cef2d
Timestamp: 1670342797 Timestamp [UCT]: 2022-12-06 16:06:37 Age [y:d:h:m:s]: 02:133:02:39:08
Block: 646777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 616816 RingCT/type: yes/0
Extra: 01fb9bd124eaaf01ca0226c46e1d99eedd59268d78a24f95a971e8d9d21d5cef2d02110000000ffaf35c9c000000000000000000

1 output(s) for total of 4.415290678000 dcy

stealth address amount amount idx
00: 5023990b45104653f1c90fb9b0c5eb3e5c09bc4b4a6a222e88edede239932f2f 4.415290678000 1087016 of 0

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": 646787, "vin": [ { "gen": { "height": 646777 } } ], "vout": [ { "amount": 4415290678, "target": { "key": "5023990b45104653f1c90fb9b0c5eb3e5c09bc4b4a6a222e88edede239932f2f" } } ], "extra": [ 1, 251, 155, 209, 36, 234, 175, 1, 202, 2, 38, 196, 110, 29, 153, 238, 221, 89, 38, 141, 120, 162, 79, 149, 169, 113, 232, 217, 210, 29, 92, 239, 45, 2, 17, 0, 0, 0, 15, 250, 243, 92, 156, 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