Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4dfa68aa2d7213be45e4828f0646a7a9bceb7d35c161e38434160e3bae4fe64

Tx prefix hash: 8c1a905be73f1fda653a15d50dfd19d5c20fb25ff1d3f2f444958cf5f55bb810
Tx public key: d4a49687a93066567b0374b80950ffb694e201b1449992ea783684a99dfefc27
Timestamp: 1724673813 Timestamp [UCT]: 2024-08-26 12:03:33 Age [y:d:h:m:s]: 01:080:21:37:37
Block: 1096297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316275 RingCT/type: yes/0
Extra: 01d4a49687a93066567b0374b80950ffb694e201b1449992ea783684a99dfefc27021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 528225c81ddc1a01563fd6b540e81cc044694d920d9d444c04e0a3ffdc4d540e 0.600000000000 1571486 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": 1096307, "vin": [ { "gen": { "height": 1096297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "528225c81ddc1a01563fd6b540e81cc044694d920d9d444c04e0a3ffdc4d540e" } } ], "extra": [ 1, 212, 164, 150, 135, 169, 48, 102, 86, 123, 3, 116, 184, 9, 80, 255, 182, 148, 226, 1, 177, 68, 153, 146, 234, 120, 54, 132, 169, 157, 254, 252, 39, 2, 17, 0, 0, 0, 5, 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