Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c94401366b5bb7213ab23a4f1c483c31990231773077f898e0c482bf18e90a32

Tx prefix hash: 9ad5dee14b503964d8f534275dd2885062cda9449e252c73d7483e03bd970f9a
Tx public key: a1b18c9290dc56fb6dc8b7551275316f08f4318475c7e82de2c27b2e8fc9c26f
Timestamp: 1722471692 Timestamp [UCT]: 2024-08-01 00:21:32 Age [y:d:h:m:s]: 00:252:05:50:06
Block: 1078041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180187 RingCT/type: yes/0
Extra: 01a1b18c9290dc56fb6dc8b7551275316f08f4318475c7e82de2c27b2e8fc9c26f021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dd9417d867b54114dd5c20a2848e9e2e065061badd8c1d51a3ac5ab29adcdd8 0.600000000000 1550596 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": 1078051, "vin": [ { "gen": { "height": 1078041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dd9417d867b54114dd5c20a2848e9e2e065061badd8c1d51a3ac5ab29adcdd8" } } ], "extra": [ 1, 161, 177, 140, 146, 144, 220, 86, 251, 109, 200, 183, 85, 18, 117, 49, 111, 8, 244, 49, 132, 117, 199, 232, 45, 226, 194, 123, 46, 143, 201, 194, 111, 2, 17, 0, 0, 0, 8, 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