Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8618a4288a3471f6b00f6ff0f8d36e2964fe802139a7b73696a6fbf4ac634e98

Tx prefix hash: 267e28ac4bd1b10225b8f9f19ad50bc10e20b36605f0ec6094446293cafb9f2e
Tx public key: 1036c7e48ce6a88b1576435ea5b3a95dca89f5a6d187969915e8dd3a91ec9042
Timestamp: 1651226197 Timestamp [UCT]: 2022-04-29 09:56:37 Age [y:d:h:m:s]: 02:293:08:43:47
Block: 490567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 729379 RingCT/type: yes/0
Extra: 011036c7e48ce6a88b1576435ea5b3a95dca89f5a6d187969915e8dd3a91ec9042021100000013c9067537000000000000000000

1 output(s) for total of 14.539454218000 dcy

stealth address amount amount idx
00: b26327dc61fadb4a699a1a798544fbf79edfa1973d70c42be9e3979453d668d6 14.539454218000 913586 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": 490577, "vin": [ { "gen": { "height": 490567 } } ], "vout": [ { "amount": 14539454218, "target": { "key": "b26327dc61fadb4a699a1a798544fbf79edfa1973d70c42be9e3979453d668d6" } } ], "extra": [ 1, 16, 54, 199, 228, 140, 230, 168, 139, 21, 118, 67, 94, 165, 179, 169, 93, 202, 137, 245, 166, 209, 135, 150, 153, 21, 232, 221, 58, 145, 236, 144, 66, 2, 17, 0, 0, 0, 19, 201, 6, 117, 55, 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